Method and apparatus for transmitting data packets and method and apparatus for receiving data packets

ABSTRACT

The invention relates to a data packet structure for conveying data of service data units (SDU) using protocol data units (PDU). The data packet comprise a data packet payload comprising at least one protocol data unit (PDU), wherein a protocol data unit (PDU) comprises a service data unit (SDU) or a fragment of a service data unit; and a data packet header comprising an indicator (FFF,SFF) indicating whether or not the data packet payload begins with a protocol data unit (PDU) being a fragment of a service data unit and whether or not the data packet payload ends with a protocol data unit (PDU) being a fragment of a service data unit.

This is a continuation application of application Ser. No. 12/067,115filed Mar. 17, 2008, which is a national stage of PCT/EP2006/008369filed Aug. 25, 2006, which is based on European Application No.05020513.7 filed Sep. 20, 2005, the entire contents of each of which areincorporated by reference herein.

FIELD OF THE INVENTION

The field of the invention is the mapping of high layer packets intolower layer frames in a communication system, which can be either awireless or fixed line network. In order to adapt the packets deliveredby the upper layer to the capabilities of the physical network (e.g.maximum frame size), it is sometimes necessary to segment or fragmentthem into several blocks that would be transmitted by separate frames.In the same way, it might be also necessary to concatenate severalpackets into one frame in order to increase transmission efficiency. Theinvention proposes a new and efficient way of indicating to thereceiving unit how segmentation and concatenation has been done at thetransmitter side.

BACKGROUND OF THE INVENTION

The necessity of adapting higher layer packets to the characteristics ofa physical network is a classical issue for all type of communicationsystems, such as wireless networks (GSM, UMTS, WiLAN, WiMax etc.) orfixed networks (IP, Frame relay, PPP, ATM, etc).

General Overview of the OSI Layer

In this section, a brief introduction is given to the OSI model (seeFIG. 1) that will be used to illustrate the explanations below.

The Open Systems Interconnection Reference Model (OSI Model or OSIReference Model for short) is a layered abstract description forcommunications and computer network protocol design. The OSI modeldivides the functions of a system into a series of layers. Each layerhas the property that it only uses the functions of the layer below, andonly exports functionality to the layer above. A system that implementsprotocol behavior consisting of a series of these layers is known as a‘protocol stack’ or ‘stack’. Its main feature is in the junction betweenlayers which dictates the specifications on how one layer interacts withanother. This means that, in principle, a layer written by onemanufacturer can operate with a layer from another. For our purpose,only the three first layers will be described.

The main purpose of the physical layer, or layer 1 is the transfer ofinformation (bit) over a specific physical medium (e.g. coaxial cables,twisted pairs, optical fibers or the air). It converts or modulates datainto signals that are transmitted over a communication channel.

The purpose of the data link layer, or layer 2 is to shape theinformation flow in a way compatible with the specific physical layer bybreaking up the input data into data frames (Segmentation AndRe-assembly or SAR functions). Furthermore it may detect and correctpotential transmission errors by requesting a retransmission of a lostframe. It provides an addressing mechanism and may offer flow controlalgorithms in order to align the data rate with the receiver capacity.Finally, when a shared medium is concurrently used by multipletransmitter and receivers, it offers mechanisms to regulate and controlaccess to the physical medium. As the span of functions of the data linklayer is large, the data link layer is often subdivided in two sublayers(e.g. RLC and MAC sublayers in UMTS). Typical examples of layer 2protocols are PPP/HDLC, ATM, frame relay for fixed line networks andRLC, LLC or MAC for wireless systems.

The network layer, or layer 3 provides the functional and proceduralmeans for transferring variable length packets from a source to adestination via one or more networks while maintaining the quality ofservice requested by the transport layer. The main purposes of thenetwork layer are to perform network routing, network fragmentation andcongestion control functions. The main examples of network layerprotocols are the IP Internet Protocol or X.25.

More information on OSI layer model can be found in “Computer Networks”,(Andrew S. Tanenbaum, fourth edition, Prentice Hall InternationalEdition, page 37-41, section 1.4.).

SDU and PDU Definition

In order to formally describe in a generic way the exchange of packetsbetween layers in the OSI model, SDU (Service Data Unit) and PDU(Protocol Data Unit) entities have been defined. An SDU is a unit ofinformation transmitted from a protocol at the layer N+1 that requests aservice to a protocol located at layer N via an SAP (Service AccessPoint). A PDU is a unit of information exchanged between peer processesat the transmitter and at the receiver of the same protocol located atthe same layer N. A PDU is generally formed by a payload part consistingof the processed version of the received SDU and control information,e.g. a layer N specific header and possibly terminated by a trailer.Since there is no direct physical connection (except for L1) betweenthese peer processes, a PDU is forwarded to the layer N−1 forprocessing. Therefore a layer N PDU is from a layer N−1 point of view aSDU. This is illustrated in FIG. 2.

Purpose of Fragmentation/Segmentation

Fragmentation, or equivalently segmentation, may be required for threedifferent reasons.

First of all, fragmentation may be required to transport datagrams orpackets though networks whose maximum allowed datagram size or maximumtransfer unit (MTU) is smaller than their size. Datagram fragmentationis typically implemented at the IP layer and is specified as the IPFragmentation in the IPv4 or IPv6 version of the standard. Similarlysegmentation is necessary when data is transported over an ATM networkin order to fit a payload size of 48 octets into the ATM cell. This isperformed in the ATM adaptation layers (AAL) between the ATM layer 2 andthe transport layer (e.g. IP).

Secondly, fragmentation may be carried out in order to balance trafficload on parallel links for instance on parallel ISDN links. The PPPmultilink protocol (MP) (“The PPP Multilink Protocol (MP)”, RFC 1990,Sklower, K., Lloyd, B., McGregor, G., Carr, D. and T. Coradetti, August1996) based on PPP describes a method for splitting, recombining andsequencing datagrams across multiple logical data links.

Finally, in wireless systems, packet segmentation potentially combinedwith concatenation is often performed at the layer 2 (e.g in RLCsublayer in UMTS, 3GPP TS 25.322, v6.4.0, “Radio Link Control (RLC)protocol specification”) in order to fit higher layer packets into theresources offered by the lower layer. As resources are typically scarcein a wireless environment, concatenation of several higher layer packetsis recommended in order to enhance the overall system efficiency.

In order for the receiver unit to separate concatenated fragments andcorrectly recombine the received fragments into the original packets,segmentation information needs to be delivered to the receiving unit.This information, usually combined with a numbering technique taggingeach fragment, enables the layer 2 at the receiver to deliver full andconsistent packets to the next higher layer.

In the following sections, several existing methods to signalsegmentation will be presented which will help to understand thedifferences to the present invention.

SAR Signaling Via Fragment Numbering

The first class of methods to indicate fragmentation regroups severalsimilar techniques that indicate the position of the fragments withinthe source packet. Two elements are necessary: the first one is an indexpointing to the position of the fragment within the source packet. Thisindex can either take the form of a fragmentation offset (IPfragmentation, see “Computer Network”, Andrew S. Tanenbaum, fourthedition, Prentice Hall International Edition, page 37-41 section 1.4.)or equivalently a fragment sequence number FSN (WiLAN, see 802.11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)specifications).

This index must be initialized to a known value (e.g. FSN=zero) for thefirst fragment of a source packet. The receiver unit uses this index torecord fragments in the correct sequence and detect lost fragments.Furthermore the last fragment of a packet is indicated with a one-bitflag (LF). An un-fragmented packet is signaled to the receiver side bysetting the index to the initial position (e.g. FSN=zero) andsimultaneously indicating that this packet is a last fragment in thesource packet. This technique is used for instance in IP fragmentationprotocol or in the ATM Adaptation Layer AAL-1. The 802.11 WiLAN MAClayer uses the same technique as well. WiLAN also appends a fieldidentifying the source packet to each fragment. This is necessary as802.11 MAC may be configured to re-order packets at the receiver sidebefore delivery to the next higher layer. This in-sequence deliveryrequirement does not exist at the IP layer, as reordering is either notrequired or performed by a higher layer (e.g. TCP).

The principle of the SAR technique via fragment numbering in WiLAN isshown in FIG. 3.

The signaling overhead is relatively significant since each fragmentmust carry at least the last fragment flag LF and the fragment sequencenumber FSN and eventually the sequence number SN of the source packet.

SAR Signaling Via Beginning/End Flags

The second class of SAR methods is widely used in various protocols suchas ATM Adaptation layer AAL-3/4, Frame Relay Frame Relay FragmentationImplementation Agreement FRF.12, Frame Relay Forum Technical Committee,WiMax and PPP multilink (MP) (“The PPP Multilink Protocol (MP)”, RFC1990, Sklower, K., Lloyd, B., McGregor, G., Carr, D. and T. Coradetti,August 1996). The main idea in this second class of SAR techniques is touse two one-bit flags to indicate for each SAR PDU, whether the PDU isthe first, the last or a middle fragment of an SDU or whether it is acomplete SAR SDU. Both flags are part of the PDU header. In someimplementations (Frame Relay and PPP multilink), one distinguishes thefunction of the two flags as one indicating the beginning of an SDU andthe other one indicating its end. The beginning fragment bit B is set to1 on the first fragment derived from an SAR SDU and set to 0 for allother fragments from the same SDU. The ending fragment bit E is set to 1on the last fragment and set to 0 for all other fragments. A PDU mayhave both the beginning and ending fragment bits set to 1. In this case,it indicates that no segmentation took place. A fragment sequencenumbering is further added in order to the receiver unit to detectfragment loss and potentially to perform PDU reordering if the link doesnot preserve the PDU sequence. After reordering, the receiver can easilycheck the B and E bits to identify which SAR PDU need to be combined tore-build the original SDUs. Figure gives an illustration of thistechnique.

SAR Signaling Via Length Indicators

A third class consists in a set of techniques that are using lengthindicator fields as pointers to indicate the boundaries of the SDUs. Agood example is the RLC (Radio Link Control) in UMTS R99. In RLC, an RLCPDU may carry segments of several SDUs or padding bits. Indeed UMTS R99operates with fixed size PDU which may not be aligned with the length ofthe SDUs to be transmitted. As radio resources are scarce, it was seenas necessary to allow concatenation of SDU at PDU level. In a genericway, a variable number of length indicators (LI) are added to the PDUheader. A length indicator is used to indicate the last octet of eachRLC SDU ending within the PDU. As usual, a sequence numbering based onthe PDU is added in the header in order to enable loss detection andreordering. The receiver can therefore perform reordering, request theretransmission of lost PDU and re-assemble the SDU. Furthermore an LIwith a special value indicates when padding is used to fill up the endof a PDU.

The main drawback of this technique is that the overhead depends on thenumber of SDU segments in a PDU, and due to this the header also has avariable size. Moreover the usage of special fields tends to raise thecomplexity of the RLC.

Finally, this technique is not very efficient when considering variablePDU size, which would be more flexible and better adapted to a fullpacket oriented environment over a wireless system. A generic example ofthis technique is shown in FIG. 5.

Concatenation Function in Wireless System

Concatenation is a function that is particularly useful for wirelesssystems. The combination of segmentation and concatenation enables thetransmitter to adapt the incoming, variable length SDUs better to theresources offered. In case of wireless system, the number of bits thatcan be transmitted over a transmission time interval (TTI) maysignificantly vary depending on the radio conditions, the code rate andthe physical resources dedicated to the transmission. For instance, amobile station close to the transmitter requires less channel encodingthan a mobile station further away. With the same allocated physicalresources and the same transmission power, the first mobile station willbe able to receive much more data than the second mobile station.Moreover, when packet services are considered, the data rate provided bythe server may in principle vary significantly over time.

In UMTS, SDU segmentation and concatenation of SDU segments into PDU areperformed at the RLC level without respect to the physical resourcesoffered and with fixed pre-defined PDU size. In order to emulate somekind of dynamic behavior, the MAC layer, based on some indications fromthe physical layer, determines the number of PDUs to be transmitted perTTI. In UMTS R99, the selected PDUs are transmitted in the form ofso-called transport channel blocks (TrCH Blk or TrBlk) to the physicallayer which concatenates them and forms a transport channel block set.In UMTS Rel-5 HSDPA, the selected PDUs are directly concatenated in theMAC layer transport channel block (TrCH Blk or TrBlk) which, thus,contains several PDUs as shown in FIG. 6. Depending on the radioconditions or other variables, the number of selected PDUs per TTIvaries as shown in FIG. 7. Therefore the sequential use of SDUsegmentation/concatenation at the RLC layer with PDU concatenation atthe MAC layer (UMTS Rel-5 HSDPA) or at the physical layer (UMTS R99)enables the transmitter to dynamically adapt the transmission toinstantaneous variables (incoming data from upper layer and resourcesoffered by lower layers).

In UMTS, the receiver unit is informed of the number of PDUs transmittedper TTI either via out-of-band signaling (Transport Format CombinationIndicator or TFCI) or in-band in a specific header (e.g. MAC-hs headerin HSDPA). It should be noted that the PDU concatenation step isgenerally performed independently of the structure of the PDUs, thus itmay happen that a SDU spans over several TTIs.

Efficient Overhead in Systems with Highly Variable Data Rate

The sequential use of SDU segmentation and PDU concatenation aspresented above works well when the range of the number of PDUs to betransmitted is not too large. However in case of highly variable systems(highly variable physical resources and highly variable data rate),which may become more common in future systems with high bandwidth, theusage of a fixed size PDU tends to be suboptimum as the size of the PDUmay not be adapted to the full range of the data rate. Indeed in thecase of packet service the size of the SDU can in principle vary from 40octets for TCP acknowledgements up to the size of the MTU (e.g. around1500 octets for Ethernet). On the physical layer side, scheduled sharedsystems such as HSDPA in UMTS offer physical resources per TTI that mayvary from few kbps to the complete bandwidth (e.g. 14 Mbps in HSDPA). Itis expected that this trend will be confirmed by future wireless system.

The problem comes from the fact that the small PDU size that would beoptimal for the lower part of the data rate span, becomes a burden whenconsidering the higher part of the data rate span. Indeed, the receiverwill have more PDUs to treat per TTI and would require more computation.Furthermore the sequence number range identifying the PDUs may becometoo short, and a wrap around problem may occur. Finally the overhead,which is equal to n*PDU header_size, increases more or less linearlywith the length of the transport channel block. Using a large PDU willforce the transmitter to either delay transmission in order to fill upthe PDU or to heavily pad the unused space in the PDU at low data rates.Increased jitter or extensive padding have a strong negative influenceon the efficiency of a radio system and should be avoided.

In general, the size of the PDU is a static parameter of the radiobearer used to carry the considered service. This parameter cannot bechanged without a heavy reconfiguration procedure. Therefore it isdifficult to efficiently adapt the link to the characteristics of theincoming SDUs or to the resources offered by the lower layer withoutstrong limitations on either the data rate or the range of physicalresources that can be allocated per TTI.

Error Propagation

The SAR signaling techniques with length indicators are sensitive toerror propagation. Indeed it may happen that the loss of a PDU forcesthe receiver to intentionally drop correctly received SDUs due to SDUborder uncertainty. As shown in FIG. 8, the loss of PDU i+2 forces thereceiver to drop the correctly received PDU i+3, since it cannotdetermine whether the fragment contained in PDU i+3 is a full SDU(alternative 1) or a segment of SDU (alternative 2).

In UMTS Rel-6, some attempts have been made to limit this issue and toreduce the overhead in some particular conditions where the SDU sizematches the PDU size. However in the general case, this problem comesfrom the fact that each PDU carries information on its own structure andwithout respect to the inner structure of the adjacent PDUs.

SAR signaling techniques with beginning/end flags or with fragmentnumbering are much more robust in this as the receiver exactly knowswhen enough PDUs are received. However, the overhead of these techniquesincreases linearly with the number of concatenated PDUs.

As can be seen, several techniques exist to signal segmentation andconcatenation. However they tend to suffer either from high overhead,lack of flexibility or may lead to increased complexity at the receiverside. Robustness towards error propagation is not given, either.

SUMMARY OF THE INVENTION

It is an object of the invention to provide efficient and feasiblesegmentation and concatenation in packet communications.

The object is solved by the subject matter of the independent claims.Advantageous embodiments of the invention are subject matters to thedependent claims.

Different embodiments of the invention provide a data packet structure,method, apparatus, system and computer readable medium for conveyingdata of service data units using protocol data units. The data packetcomprises a packet payload comprising at least one protocol data unit,wherein a protocol data unit comprises a service data unit or a fragmentof the service data unit and a data packet header comprising anindicator indicating whether or not the data packet payload begins witha protocol data unit being a fragment of a service data unit and whetheror not the data packet payload ends with a protocol data unit being afragment of the service data unit.

According to an advantageous embodiment the indicator consist of twoflags, wherein the first flag indicates whether the data packet payloadbegins with the protocol data unit being a fragment of a service dataunit and the second flag indicates whether the data packet payload endswith a protocol data unit being a fragment of the service data unit.

The advantage of this embodiment is that the flag, when set, indicates aprotocol data unit being a fragment of the service data unit.

According to another advantageous embodiment the data packet structurecomprises a sequence number indicator indicating the position of thedata packet in a sequence of data packets.

In a further advantageous embodiment the method for transmitting datapackets comprising service data units comprises the steps of forming atleast one protocol data unit comprising a service data unit or afragment of a service data unit, forming a data packet payloadcomprising at least one protocol data unit, forming a data packet headercomprising at least an indicator for indicating whether or not the datapacket payload begins with a protocol data unit being a fragment of aservice data unit and whether or not the data packet payload ends with aprotocol data unit being a fragment of the service data unit, forming adata packet comprising the data packet header and the data packetpayload, and transmitting the data packet over a channel.

According to another advantageous embodiment the data packet payloadcomprises a plurality of protocol data units and the data packet beginswith a first protocol data unit and ends with a last protocol data unit.

In a further a advantageous embodiment the step of forming the datapacket payload of a predetermined size further comprises the followingsub-steps a), b) and c). In a) it is determined whether the sizeremaining in the data packet payload is sufficient to transport a nextservice data unit or a fragment remaining from a previous service dataunit. If this is the case, in b) a next protocol data unit comprisingthe next service data unit or a fragment of a previous service data unitis formed and the protocol data unit is added to the data packetpayload. Otherwise, a next service data unit or fragment remaining froma previous service data unit is fragmented and a protocol data unit isformed comprising a first fragment of the service data unit or fragmentremaining from a previous service data unit such that the size of theprotocol data unit corresponds to the remaining size of the data packetpayload and the protocol data unit is added to the data packet payload.Steps a) and b) are repeated until the data packet payload has aninsufficient size remaining to transport a next service data unit.

It is further advantageous that, upon having filled the data packetpayload with protocol data units, the indicators to indicate whether ornot the data packet payload begins with the protocol data unit being afragment of the service data unit and whether or not the data packetpayload ends with a protocol data unit being a fragment of the servicedata unit are set.

In another advantageous embodiment the data packet payload isdynamically fixed by a resource allocation entity depending on radioconditions and buffer occupancy.

In a further advantageous embodiment, a method for receiving datapackets comprising a data packet header and a data packet payload,wherein the data packet payload comprises at least one protocol dataunit comprising either a service data unit or a fragment of a servicedata unit is described. The method comprises the steps of receiving datapackets over a channel, each data packet comprising a data packetpayload and a data packet header, the data packet header comprising asequence number indicator indicating the position of the data packet ina data packet sequence, and an indicator wherein the indicator indicateswhether or not the data packet payload begins with the protocol dataunit being a fragment of a service data unit and whether or not the datapacket ends with the packet payload being a fragment of the service dataunit, saving the protocol data units of the received data packet payloadwith previously received protocol data units in a reception bufferin-sequence according to the sequence number indicator, and markingwhether a first protocol data unit of the received data packet payloadis to be combined with the previous in-sequence protocol data unit andwhether a last protocol data unit of the received data packet payload isto be combined with a next in-sequence protocol data unit.

According to a further advantageous embodiment the reception buffer isanalysed as to whether the protocol data unit is marked and if it is theprotocol data unit is combined with the other marked protocol data unitto form a service data unit.

In another advantageous embodiment, an apparatus for transmitting datapackets comprising service data units is described. The apparatuscomprises a protocol data unit forming means adapted to form a protocoldata unit comprising a service data unit or a fragment service dataunit, a data packet payload forming means adapted to form a data packetpayload comprising at least one protocol data unit, data packet headerforming means adapted to form a data packet header comprising anindicator for indicating whether or not the data packet payload beginswith a protocol data unit being a fragment of a service data unit andwhether or not the data packet payload ends with a protocol data unitbeing a fragment of a service data unit, data packet forming meansadapted to form a data packet comprising the data packet header and thedata packet payload, and transmitting means adapted to transmit the datapackets over a channel.

A further embodiment of this invention relates to an apparatus forreceiving data packets comprising a data packet header and a data packetpayload, wherein a data packet payload comprises at least one protocoldata unit comprising either a service data unit or a fragment of aservice data unit. The apparatus comprises receiving means adapted toreceive data packets over a channel, each data packet comprising a datapacket payload and a data packet header, the data packet headercomprising a sequence number indicator indicating the position of thedata packet in a data packet sequence, and an indicator, wherein theindicator indicates whether or not the data packet payload begins with aprotocol data unit being a fragment of a service data unit and whetheror not the data packet ends with the protocol data unit being a fragmentof the service data unit. It further comprises a reception bufferadapted to save the protocol data units of the received data packetpayload with previously received protocol data units in-sequenceaccording to the sequence number indicator, and marking means adapted tomark whether a first protocol data unit of the received data packetpayload is to be combined with the previous in-sequence protocol dataunit and whether a last protocol data unit of the received data packetpayload is to be combined with a next in-sequence protocol data unit.

Another embodiment of the invention relates to a computer readablemedium storing instructions that, when executed by a processor of atransmitting apparatus, cause the transmitting apparatus to transmitdata packets comprising service data unit. This is done by forming atleast one protocol data unit comprising a service data unit or afragment of a service data unit, forming a data packet payloadcomprising protocol data units, forming a data packet header comprisingat least an indicator for indicating whether or not data packet payloadbegins with a protocol data unit being a fragment of the service dataunit and whether or not the data packet payload ends with a protocoldata unit being a fragment of the service data unit, and transmittingthe data packets over a channel.

A further advantageous embodiment relates to a computer readable mediumstoring instructions that, when executed by a processor of a receivingapparatus, cause the receiving apparatus to receive data packetscomprising a data packet header and a data packet payload, wherein thedata packet payload comprises at least one protocol data unit comprisingeither a service data unit or a fragment of a service data unit isdescribed. The method comprises the steps of receiving data packets overa channel, each data packet comprising a data packet payload and a datapacket header, the data packet header comprising a sequence numberindicator indicating the position of the data packet in a data packetsequence, and an indicator wherein the indicator indicates whether ornot the data packet payload begins with the protocol data unit being afragment of a service data unit and whether or not the data packet endswith the packet payload being a fragment of the service data unit,saving the protocol data units of the received data packet payload withpreviously received protocol data units in a reception bufferin-sequence according to the sequence number indicator, and markingwhether a first protocol data unit of the received data packet payloadis to be combined with the previous in-sequence protocol data unit andwhether a last protocol data unit of the received data packet payload isto be combined with a next in-sequence protocol data unit.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following, the invention is described in more detail withreference to the attached figures and drawings. Similar, ourcorresponding details and the figures are marked with the samereferences.

FIG. 1—shows the OSI layer model;

FIG. 2—shows SDU and PDU in the OSI layer model;

FIG. 3—shows SAR signaling by fragment numbering;

FIG. 4—shows SAR signaling with Beginning and End flags;

FIG. 5—shows SAR signaling with length indicators;

FIG. 6—shows the SDU Segmentation and PDU concatenation Processes;

FIG. 7—shows Transport Channel Block generation;

FIG. 8—shows error propagation in UMTS R99;

FIG. 9—shows the SAR and concatenation processes of an embodiment of thepresent invention;

FIG. 10—shows the SAR and concatenation flow with Fragmentation Flag ofan embodiment of the present invention;

FIG. 11—shows SAR signaling with Fragmentation Flags according to anembodiment of the present invention; and

FIG. 12—is a flow diagram for the segmentation and concatenationprocess.

DETAILED DESCRIPTION OF THE INVENTION

The present invention is applicable to any data packet communicationsystem using variable length transmission frames, for example, wirelessnetworks such as GSM, UMTS, WiLAN, WiMAX, etc. or fixed networks such asIP, frame relay, PPP, ATM etc.

The different embodiments of the invention are described based on theOSI layer model, especially the exchange of packets between an SDU andPDU layer. Please see the background section for a more detaileddescription of the relevant parts of the OSI layer model as well as SDUsand PDUs. The background section also describes the reasons foremploying fragmentation and/or segmentation in communication networks.

In this invention, a method is proposed that enables an efficientSegmentation and Concatenation procedure at the fixed signaling cost,which makes the overhead decrease in percent with the length of thetransmitted TrBlk.

SDU segmentation and PDU concatenation both depend on the physicalresources that are allocated for transmission for the next TTI. Forinstance the size of the payload of the next transport channel block(Size_ind) can be indicated to the SAR function as shown in FIG. 9.

Based on this indication, the SAR function selects n SDUs, the totalsize of which is just above Size_ind. If the sum of the length of the nSDUs is greater than size_ind, the SAR function segments the last SDU intwo fragments. The sum of the n−1th SDUs and the first fragment of thenth SDU is equal to Size_ind. Each of them is transformed into a PDU andreceives a sequence number attributed sequentially. For the nexttransmission, the second fragment will be considered first. This isshown in FIG. 10, where the SDU3 is fragmented in 2 PDUs (PDU3 andPDU4).

Therefore by construction, all formed PDUs are full SDUs except thefirst and the last ones in a transport block (TrBlk), which may be afragment of an SDU. All the others are full SDUs therefore it issufficient to indicate to the receiver whether the first and the lastPDUs in a transport block are fragments of an SDU or a full SDU. Thiscan be done easily by 2 one-bit flags or fragmentation flags attached tothe TrBlk header. The first fragmentation flag, or FFF, indicateswhether the first SAR PDU in the TrBlk is a fragment of an SDU or notand the second fragmentation flag (SFF) indicates whether the last SARPDU in the TrBlk is a fragment of an SDU or not.

This process can be described in a generalized form along the lines ofFIG. 12. SDUs or fragments of SDUs are taken from a buffer and it isthen determined whether the SDU or fragment of an SDU fits in theremaining size of the transport block, which might be the whole of thetransport block or only a part thereof. If the full SDU or fragment ofthe SDU fits in the remaining size of the transport block, a PDU iscreated from this SDU. This PDU is then inserted in the transport block.

The transport block is checked whether there is any size remaining. Ifthere is, the process starts over again, if there is not, the indicatorsare added and the transport block is transmitted with the indicators.

If however, the SDU or fragment of the SDU does not fit in the remainingsize of the transport block, the SDU is fragmented and a PDU is createdfrom a fragment of the SDU to fit into the remaining size of thetransport block. The second fragment of the SDU is put in the buffer andthe PDU is then inserted into the transport block and the indicatorsadded.

The first fragmentation flag (FFF) indicates whether the first PDU inthe transport block is a fragment of SDU or not and the secondfragmentation flag (SFF) indicates whether the last PDU in the transportblock is a fragment of an SDU or not.

Finally, the transport block is transmitted with the indicators and theprocess can start again.

When receiving a transport block n with the FFF set to 1, the receiverknows that the first SAR PDU in the TrBlk must be combined with the lastSAR PDU of the previous TrBlk n−1. This TrBlk may have also indicatedthat the last SAR PDU in this TrBlk is a fragment of an SDU by settingthe SFF to 1.

In a lossless system, FFF and SFF provide redundant information and arenot really needed. However in a lossy system such as a wireless system,this is helpful to prevent error propagation. Indeed, if the (n−1)thTrBlk in the previous example had been lost, the receiver unit wouldhave detected this loss thanks to the SAR PDU sequence numbering, andthe FFF in the nth TrBlk would have indicated that the first PDU can bediscarded as the corresponding SDU is incomplete. However the second andsubsequent PDU in the nth TrBlk will be kept and used in the re-assemblyfunction.

If only one PDU is transmitted per SDU, FFF and SFF may still havedifferent values. FFF would indicate whether the PDU should be combinedwith the last PDU of the previous TrCh Blk and SFF would indicatedwhether the PDU should be combined with the first PDU of the next TrChBlk.

One important aspect of the invention is to signal SAR information notat PDU level (i.e in the PDU header) but rather in the TrBlk header. Byusing variable size PDU and simple segmentation and concatenation rules,it is proposed to indicate SAR information with only 2 bits per TrBlkheader, which indicate the status (fragmented, not fragmented) of thefirst and the last PDU that are concatenated in the TrBlk.

Compared to the prior art solution, the SAR information is only 2 bitsper TrBlk, which has to be compared to 2*n bits per TrBlk for the SARsignaling with beginning/end flags, where n is the number of PDU in theTrBlk. This is a significant decrease when many PDUs are concatenated inthe same TrBlk.

As can be seen, it is assumed that the SAR PDU size is variable. Forexample, in the current state of UMTS, the size of the PDU is fixed andis a static parameter of the bearer used to carry the service. There issometimes a need to inform the receiver where the PDU boundaries can befound. Then it is required to indicate the length of each PDU in the SARPDU header with length indicators as shown in FIG. 11. This is actuallyequivalent to the length indicator fields that are used in the SARsignaling techniques with length indicators to signaled SDU boundarieswithin each PDU.

Moreover it would be possible to further save space by signaling onlyone SAR PDU sequence number per TrBlk. The sequence number of the firstPDU or the last PDU in the TrBlk can be used for this purpose. Thereceiver can count the number of length indicators contained in theTrBlk to get the number of concatenated PDUs or a small field Nindicating this number can be added in the TrBlk header as shown as inFIG. 11.

Another embodiment of the invention relates to the implementation of theabove described various embodiments using hardware and software. It isrecognized that the various above mentioned methods may be implementedor performed using computing devices (processors) as for example generalpurpose processors, digital signal processors (DSP), applicationsspecific integrated circuits (ASIC), field programmable gate arrays(FPGA) or other programmable logic devices etc. The various embodimentsof the invention may also be performed or embodied by a combination ofthese devices.

Further, the various embodiments of the invention may also beimplemented by means of software modules, which are executed by aprocessor or directly in hardware. Also, a combination of softwaremodules and a hardware implementation may be possible.

The software modules may be stored on any kind of computer-readablestorage media, for example RAM, EPROM, EEPROM, flash memory, registers,hard disks, CD-ROM, DVD etc.

1. A method for transmitting data packets, the method comprising thesteps of: mapping one of (i) a plurality of full service data units,(ii) a plurality of segments of service data units, or (iii) at leastone full service data unit and at least one segment of a service dataunit to a data packet payload, the service data units in each of options(i), (ii) or (iii) including a first service data unit and a lastservice data unit; mapping a single indicator consisting of a first bitand a second bit to a data packet header, when the number of the servicedata units in the data packet payload is more than two; mapping the datapacket header and the data packet payload to a data packet; andtransmitting the data packet by a transmitter, wherein: the first bitand the second bit of the indicator indicate only (i) whether or not thedata packet payload begins with a segment of the first service dataunit, and (ii) whether or not the data packet payload ends with asegment of the last service data unit.
 2. The method according to claim1, wherein the indicator is included only in the data packet header. 3.The method according to claim 1, wherein, the data packet payloadcomprises one of said plurality of segments of service data units, orsaid at least one full service data unit and at least one segment of aservice data unit, and the indicator indicates whether or not the datapacket payload is to be reassembled with the data packet payload of apreviously sent data packet and whether or not the data packet payloadis to be reassembled with the data packet payload of a next data packet.4. An apparatus for transmitting data packets, the apparatus comprising:a data packet payload mapping section that maps one of (i) a pluralityof full service data units, (ii) a plurality of segments of service dataunits, or (iii) at least one full service data unit and at least onesegment of a service data unit to a data packet payload, the servicedata units in each of options (i), (ii) or (iii) including a firstservice data unit and a last service data unit; a data packet headermapping section that maps a single indicator consisting of a first bitand a second bit to a data packet header, when the number of the servicedata units in the data packet payload is more than two; a data packetmapping section that maps the data packet header and the data packetpayload to a data packet; and a transmitter that transmits the datapacket, wherein: the first bit and the second bit of the indicatorindicate only (i) whether or not the data packet payload begins with asegment of the first service data unit, and (ii) whether or not the datapacket payload ends with a segment of the last service data unit.
 5. Theapparatus according to claim 4, wherein, the data packet payloadcomprises one of said plurality of segments of service data units, orsaid at least one full service data unit and at least one segment of aservice data unit, and the indicator indicates whether or not the datapacket payload is to be reassembled with the data packet payload of apreviously sent data packet and whether or not the data packet payloadis to be reassembled with the data packet payload of a next data packet.6. The apparatus according to claim 4, wherein the apparatus is awireless terminal in a communication system.
 7. The apparatus accordingto claim 4, wherein the apparatus is a wireless base station in acommunication system.
 8. A method for receiving data packets comprisinga data packet header and a data packet payload, the method comprisingthe steps of: receiving data packets by a receiver, each data packetcomprising: a data packet payload comprising one of (i) a plurality offull service data units, (ii) a plurality of segments of service dataunits, or (iii) at least one full service data unit and at least onesegment of a service data unit, the service data units in each ofoptions (i), (ii) or (iii) including a first service data unit and alast service data unit; and a data packet header comprising a singleindicator consisting of a first bit and a second bit when the number ofthe service data units in the data packet payload is more than two,wherein the first bit and the second bit of the indicator indicate only(i) whether or not the data packet payload begins with a segment of thefirst service data unit, and (ii) whether or not the data packet payloadends with a segment of the last service data unit.
 9. The methodaccording to claim 8, wherein the method further comprises, bufferingthe (i) plurality of full service data units, (ii) plurality of segmentsof service data units, or (iii) at least one full service data unit andat least one segment of a service data unit of the received data packetpayload with previously received at least one full or segment of aservice data unit in a reception buffer.
 10. An apparatus for receivingdata packets comprising a data packet header and a data packet payload,the apparatus comprising: a receiver that receives data packets, eachdata packet comprising: a data packet payload comprising one of (i) aplurality of full service data units, (ii) a plurality of segments ofservice data units, or (iii) at least one full service data unit and atleast one segment of a service data unit, the service data units in eachof options (i), (ii) or (iii) including a first service data unit and alast service data unit; the number of the service data units in the datapacket payload is more than two, wherein the first bit and the secondbit of the indicator indicate only (i) whether or not the data packetpayload begins with a segment of the first service data unit, and (ii)whether or not the data packet payload ends with a segment of the lastservice data unit.
 11. The apparatus according to claim 10, wherein theapparatus further comprises a reception buffer that buffers the (i)plurality of full service data units, (ii) plurality of segments ofservice data units, or (iii) at least one full service data unit and atleast one segment of a service data unit of the received data packetpayload with previously received at least one full or segment of aservice data unit.
 12. The apparatus according to claim 10, theapparatus is a wireless terminal in a communication system.
 13. Theapparatus according to claim 10, the apparatus is a wireless basestation in a communication system.